Physical lock electronic interface tool

ABSTRACT

A physical lock interface system facilitates secure and remote control of assignment and enablement of physical lock systems. The system receives a request to enable a user to disable a physical lock during a particular range of time. The lock is associated with a geofence boundary defined by a geofence. During the range of time, the system monitors for a presence of the user within the geofence. In response to determining that the user is within the geofence during the range of time, the system transmits a communication to an application of a client device of the user. The application is configured to interact electronically with the physical lock and to cause the client device to display information identifying the physical lock based on the communication. The system detects an electronic signal initiated by the application while the user is within the geofence and disables the physical lock.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.63/010,657, filed Apr. 15, 2020, which is incorporated herein byreference in its entirety.

BACKGROUND 1. Field of Art

This disclosure relates generally to physical lock systems and moreparticularly to enabling secure remote operation of a physical lock.

2. Description of Art

Physical locking mechanisms are used to secure and store physical items.However, logistics of maintaining physical keys and ensuring that onlyauthorized users can disable a lock can be costly and prone to errors orinterference by bad actors. This can be especially true for entitiesthat maintain and use many locks at once. It is additionally difficultto manage transfer of authorized access to locks. For physical keys,typically, one party must meet up or communicate directly with a secondparty to transfer a key or an entry code in order for the second partyto be able to enable or disable the lock. For electronic access codes,additional security risks exist in that access codes can be interceptedand used by unauthorized parties.

SUMMARY

Systems and methods are disclosed herein for enabling secure and remotecontrol of assignment and enablement of physical lock systems. Oneembodiment of a disclosed system, method, and computer readable storagemedium disclosed herein includes receiving, by a physical lock interfacesystem, a request to enable a user to disable a physical lock during aparticular range of time. The lock is associated with a boundary definedby a geofence. During the range of time, the physical lock interfacesystem monitors for a presence of the user within the geofence. Inresponse to determining that the user is within the geofence during therange of time, the physical lock interface system transmits acommunication to an application of a client device of the user, that is,an application installed on a client device of the user or anapplication that is otherwise accessible by the user via the clientdevice. The application of the client device of the user is configuredto interact electronically with the physical lock and is also configuredto cause the client device to display information identifying thephysical lock based on the communication. The disclosed system, methodand computer readable storage medium further includes detecting, by thephysical lock interface system that manages the physical lock, anelectronic signal initiated by the application while the user is withinthe geofence and, responsive to detecting the electronic signal,disabling the physical lock.

In an embodiment, the physical lock, when disabled, provides access tothe user to a physical key for accessing a vehicle. In this embodiment,the system, method, and computer readable medium further include, priorto detecting the electronic signal initiated by the application whilethe user is within the geofence, detecting a disabling of the physicallock. For example, the physical lock interface system might be incommunication with sensors on the lock that provide a notification whena lock is tampered with or otherwise disabled in an unauthorized manner.Responsive to detecting the disabling of the physical lock prior todetecting the electronic signal initiated by the application while theuser is within the geofence, the physical lock interface systemtransmits a communication to a server such as a server associated withan original equipment manufacturer of a vehicle or other administratorof a vehicle security system, to prevent access to a vehicle by way ofthe physical key without additional verification. For example, anonboard computer for a loaner car may receive the communication that thelock on a box storing the key to the car was disabled without the userhaving been present in the geofence associated with the lock, possiblyindicating that the lock was tampered with and the key was stolen. Theonboard computer can prevent access to the car using the potentiallycompromised key until additional verification is received by thecontactless server system. The physical lock interface system mayadditionally transmit a communication to the application of the clientdevice to cause the client device to display a request for the user toenter a verification code. The verification code is used by the physicallock interface system to verify that an authorized user is accessing thelock and that the lock was not tampered with. The physical lockinterface system receives the additional verification comprising theverification code and, responsive to the receipt of the additionalverification, transmits a communication to the server to prevent accessto enable access to the vehicle by way of the physical key.

In an embodiment, monitoring for a presence of the user, for examplewithin the geofence, comprises receiving a photo of an area within theboundary defined by the geofence from a camera that is positioned tocapture images of vehicles entering the boundary defined by thegeofence. The system, method, and computer readable medium furtherincludes analyzing the photo to determine a unique identifier of thevehicle shown in the photo and determining that the unique identifier ofthe vehicle matches a unique identifier of a vehicle that is known to beassociated with the user. That is, the physical lock interface systemmay identify the presence of the user within the geofence boundary bymonitoring for and identifying a vehicle known to be associated with theuser.

Prior to disabling the physical lock, the disclosed system, method, andcomputer readable storage medium, in one embodiment, includesdetermining that one or more documents of a predefined set of documentshas not been completed by the user. The physical lock interface systemtransmits a communication to the application of the client device tocause the client device to display information identifying the one ormore incomplete documents. For example, the system may require a user tofill out and execute a form such as a waiver before the lock can bedisabled and the system may send an incomplete form to the user deviceof the user so that the form can be completed electronically. Prior todisabling the physical lock, the physical lock interface systemdetermines that the one or more incomplete documents are subsequentlycompleted by the user.

In one embodiment, the disclosed system, method, and computer readablemedium further includes, transmitting, in response to determining thatthe user is within the geofence during the range of time, transmitting acommunication to a system that manages the physical lock to activate alight associated with the physical lock. The light identifies thephysical lock from among a plurality of physical locks. For example, aphysical lock securing a mailbox may be placed among many othermailboxes with other physical locks. Activating a light on the physicallock will help the user to easily identify the physical lock on thecorrect mailbox.

One embodiment of a disclosed system, method and computer readablestorage medium is disclosed herein for, prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, detecting a disabling of the physical lock. Responsive todetecting the disabling of the physical lock prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, the disclosed embodiment includes transmitting acommunication to an application of a client device of an operatorassociated with management of the physical lock. The application isconfigured to cause the client device of the operator to displayinformation identifying the physical lock based on the detection, andthe communication includes instructions to display the informationidentifying the physical lock based on the detection. For example, ifthe physical lock interface system receives a notification that a lockhas possibly been tampered with, a communication may be transmitted to amanager of the physical lock, alerting the manager of the possibilitythat the lock has been damaged or accessed in an unauthorized manner.

The features and advantages described in this summary and the followingdetailed description are not limiting and not all-inclusive. Manyadditional features and advantages will be apparent to one of ordinaryskill in the art in view of the drawings, specification, and claimshereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level block diagram of a system environment for aphysical lock interface system, in accordance with an exampleembodiment.

FIG. 2 is a high-level block diagram of a system architecture for thephysical lock interface system, in accordance with an exampleembodiment.

FIG. 3 illustrates a system environment for locks associated with thephysical lock interface system, in accordance with an exampleembodiment.

FIG. 4 is a block diagram illustrating components of an example machineable to read instructions from a machine-readable medium and executethem in one or more processors (or controllers).

FIG. 5 is a flowchart illustrating a method facilitating disablement ofa physical lock, in accordance with an example embodiment.

The figures use like reference numerals to identify like elements. Aletter after a reference numeral, such as “104A,” indicates that thetext refers specifically to the element having that particular referencenumeral. A reference numeral in the text without a following letter,such as “104,” refers to any or all of the elements in the figuresbearing that reference numeral.

The figures depict an embodiment for purposes of illustration only. Oneskilled in the art will readily recognize from the following descriptionthat alternative embodiments of the structures and methods illustratedherein may be employed without departing from the principles describedherein.

DETAILED DESCRIPTION

FIG. 1 is a high-level block diagram of a system environment for aphysical lock interface system 130, in accordance with an exampleembodiment. The physical lock interface system 130 facilitates secureand remote control of physical locks. The physical lock interface system130 manages assignment of physical locks to users and handlesverification and authentication of users requesting to disable thephysical locks. In the example of FIG. 1 , the system environment of thephysical lock interface system 130 includes a client device 110, anoperator device 115, a network 120, a lock 140, and the physical lockinterface system 130. For clarity, although only one client device 110,one operator device 115, and one lock 140 are shown in FIG. 1 ,embodiments of the system environment can have any number of clientdevices 110, operator devices 115, and locks 140. The functionsperformed by the various entities of FIG. 1 may vary in differentembodiments.

Client devices 110 are user devices that allow client users to interactwith the physical lock interface system 130. A client user interactingwith a client device 110 may generally be a customer, vendor, or otheroutside entity interacting with the entity that operates and controlsthe locks 140. The client devices 110 are mobile electronic computingdevices, such as smartphones, tablets, and computers that are configuredto communicate with the physical lock interface system 130 via a network120. In some embodiments, a client device 110 may be an onboard computerof a vehicle. Client devices 110 may include global positioning system(GPS) receivers or other means of location detection.

The operator devices 115 are user devices that allow operators tointeract with the physical lock interface system 130. The operatordevices 115 are computing devices associated with administration,operation, and management of the physical lock interface system 130and/or associated with management of the locks 140. An operator device115 is generally operated by an operator who may be an administrativeuser such as a user associated with an entity that hosts locks 140. Forexample, an operator device 115 may be a smartphone of a clerk who helpsto manage locks 140 and administration of a physical lock interfacesystem 130 for a company. Although both client device 110 and operatordevices 115 are sometimes referred to separately herein, they can beunderstood to be two use cases of a user device that providesinteraction by a user with the physical lock interface system 130. Invarious embodiments, the operator devices 115 have the samefunctionalities as the client devices 110 as described herein.Similarly, in various embodiments, the client devices 110 have the samefunctionalities as the operator devices as described herein. An operatordevice 115 may be a computer, a mobile computing device such as asmartphone, tablet, or laptop, a server, a client device or anothercomputing system that can communicate with the physical lock interfacesystem 130 either locally or over a network 120.

The network 120 may comprise any combination of local area and wide areanetworks employing wired or wireless communication links. In someembodiments, all or some of the communication on the network 120 may beencrypted.

The physical lock interface system 130 facilitates user and operatorinteractions with locks 140. A physical lock 140 may be any physicallocking mechanism that can be enabled and disabled remotely, forexample, in response to receipt of an electronic signal from thephysical lock interface system 130. In some embodiments, a lock 140 isone of a set of multiple locks that are associated with the physicallock interface system 130. A set of locks 140 may be grouped together atone physical location or may be spread out in various situations. Forexample, at a dealership that provides vehicle service a row oflockboxes secured by locks 140 may be provided for customers to securelypick up and drop off keys to their vehicles for servicing. As anotherexample, each mailbox in a mailroom may be secured with a lock 140,forming a wall of stationary locks. As another example, a lock 140 maybe attached to and used to secure one of a fleet of bicycles in a bikeshare program, and thus the set of locks 140 associated with thebicycles in the program may be distributed around a city as the bicyclesare accessed and moved. Each lock 140 in a set of locks 140 may includean identification appliance so that the lock 140 can be identified fromamong the other locks 140 in the set of multiple locks. Examples ofidentification appliances include a light, a speaker, and an electronicdisplay. The identification appliance may be coupled to the mechanism ofthe lock 140 or may be nearby the lock 140, for example, on a door of amailbox that is secured with a lock 140.

The physical lock interface system 130 manages access to a set of locks140. The physical lock interface system 130 is a computing system thatis configured to communicate with client devices 110, operator devices115, and locks 140 over a network 120. The physical lock interfacesystem 130 may be associated with an entity or organization that managesthe set of locks 140. When a client device 110 or an operator device 115requests a lock assignment for a user, the physical lock interfacesystem 130 prepares and allocates a lock 140 to the user. The physicallock interface system 130 also stores information about geofenceboundaries associated with the lock 140, and stores information aboutconditions that need to be met for the lock to be disabled. For example,a user may be required to complete and submit a form and be within ageofence boundary associated with the lock 140 before the physical lockinterface system 130 will disable the lock 140 assigned to the user.

FIG. 2 is a high-level block diagram of a system architecture for thephysical lock interface system 130, in accordance with an exampleembodiment. The system architecture includes various modules and datastores to manage user interactions with physical locks 140. The physicallock interface system 130 includes a device communication module 205, ageofence management module 210, a geofence datastore 215, a lockassignment module 220, a lock assignment datastore 225, a lockidentification module 230, a signal detection module 235, a lockmanagement module 240, a lock interaction detection system 245, and anOEM communication module 250. Computer components such as web servers,network interfaces, security functions, load balancers, failoverservers, management and network operations consoles, and the like arenot shown so as to not obscure the details of the system architecture.Additionally, the physical lock interface system 130 may contain more,fewer, or different components than those shown in FIG. 2 and thefunctionality of the components as described herein may be distributeddifferently from the description herein. Furthermore, the components ofFIG. 2 can be included, additionally or alternatively, in any suitablecomponent shown in FIG. 1 . Additionally, some or all functionality ofthe modules of FIG. 2 may be performed by an application installed onuser devices such as a client device 110 and an operator device 115.

The device communication module 205 facilitates communication betweenthe physical lock interface system 130 and the client devices 110 andoperator devices 115. The client devices 110 transmit requests to thephysical lock interface system 130. For example, a client device 110 maytransmit a request to the device communication module 205 requesting fora physical lock 140 associated with a user of the client device 110 tobe disabled. The client devices 110 and physical lock interface system130 can also communicate via the device communication module 205 aboutinformation related to assignment of locks 140, requests andconfirmation about whether required conditions have been met for a lock140 to be disabled, and information about geofence boundaries associatedwith the locks 140. The device communication module 205 also transmitsmessages between the physical lock interface system 130 and operatordevices 115. Examples of information communicated between the operatordevices 115 and the device communication module 205 includenotifications about locks 140 that have been enabled or disabled,administrative communications, and scheduling tasks. For example, anoperator may schedule a lock 140 assignment for a user via an operatordevice 115 in communication with the device communication module 205. Asanother example, the physical lock interface system 130 may beconfigured to notify an operator device 115 via the device communicationmodule 205 when a sensor at a lock 140 senses that the lock has beendisabled.

The geofence management module 210 manages geofence boundaries that areassociated with the locks 140. Managing the geofence boundaries includesestablishing geofence boundary parameters and monitoring informationthat is received from client devices 110 related to the location of theclient devices with respect to the geofence boundary. The geofencemanagement module 210 generates a geofence to be stored in relation to alock 140. A geofence comprises a geofence boundary that defines avirtual geographic perimeter. A perimeter may be defined by a radiuswith a lock 140 at the center, or may be defined by another shapespecified around the area associated with the lock 140 or multiple locks140. A global positioning system (GPS) transmitter on client device canprovide a location of the client device and when the geofence managementmodule 210 is notified that the client device 110 location is surroundedby the defined geofence perimeter, then the client device 110 is withinthe geofence. The geofence management module 210 may associate aseparate geofence boundary with each lock 140, or, in alternateembodiments, one geofence boundary may be associated with multiple locks140, such as when a group of locks 140 are all physically located nearto each other and can thus be surrounded by the same boundary (e.g., abank of post office boxes). In some cases, a new geofence boundary maybe established by the geofence management module 210, for example eachtime a lock 140 is reassigned to a new user. In one embodiment, thegeofence management module 210 may confirm whether a client device 110is within a designated geofence boundary, given information about thecurrent location of the client device 110.

In some embodiments, the geofence management module 210 monitorslocation detection of client devices 110 and/or users associated withclient devices using techniques other than or in addition to GPSsensing. In one embodiment, the geofence management module 210 managesone or more beacons. The geofence management module 210 associates asignal radius of the beacon with the geofence boundary for that beaconand a location may include multiple beacons to cover a larger area. Whena client device 110 connects with a beacon, the geofence managementmodule 210 identifies the client device 110 as being within the range ofthe geofence boundary associated with the beacons. A client device 110using an application associated with the physical lock interface system130 may connect with a beacon by transmitting a query that a beacon maydetect and respond to. Alternatively, beacons may continuously transmitpings and any applications on client devices 110 within range of thebeacon may detect the ping when the application is active. In anotherembodiment, the physical lock interface system 130 may include othersensors such as cameras which can capture photos or video to determinewhether a user associated with a certain lock 140, client device 110, oroperator device 115 is within a designated boundary. For example, thegeofence management module 210 receives images from a camera that filmsan entrance to a parking lot. The geofence management module 210executes image recognition software that may be trained, for example, todetect license plate numbers and match the numbers to known user licenseplates to determine that a user is within the lot boundary associatedwith a lock 140. In still another example embodiment, the geofencemanagement module 210 determines that a user has connected to an IPaddress associated with the physical lock interface system 130 todetermine that the user is within a designated area for interacting witha lock 140.

The geofence management module 210 stores data about geofences in thegeofence datastore 215. The geofence datastore 215 may store informationincluding associations of geofence boundaries with specific locks 140,geofence boundary parameters, and information about whether clientdevices 110 are currently located within the geofence boundaries. Inembodiments using GPS sensing to determine the location of clientdevices within geofence boundaries, the geofence datastore 215 may storegeographic coordinates that define the geofence boundaries. Inembodiments that employ beacons for detecting the proximity of clientdevices 110, the geofence datastore 215 may store information about theone or more beacons that together define the geofence boundaries.

The lock assignment module 220 allocates locks 140 to users of clientdevices 110 and manages lock 140 access rules associated with theassignments. Depending on the use case, the physical lock interfacesystem 130 may reassign locks to be associated with different users atdifferent times. When the device communication module 205 receives arequest from a client device 110 or from an operator device 115 toassign a lock to a user of a client device 110, it may transmit therequest to the lock assignment module 220. The lock assignment module220 determines whether any physical locks 140 are available at therequired time and selects one of the available locks 140 to assign tothe user in response to the request. In performing lock 140 assignments,the lock assignment module 220 also manages scheduling of futureassignments. For example, if a rental car center uses locks 140 tosecure boxes holding rental car keys, the lock assignment module 220 mayschedule a lock 140 to be associated with a renter within a future timewindow when the user is expected to pick up the rental car.

In addition to scheduling lock 140 assignments, the lock assignmentmodule 220 establishes conditions associated with disabling each lock140. The conditions for disabling a lock 140 may be generated at thetime that the lock 140 is scheduled for assignment to a user of a clientdevice 110 or operator device 115 and conditions associated withdisabling the lock 140 may be added or amended over time. Examples ofconditions for disabling a lock 140 may include the presence of theclient device 110 within a geofence boundary associated with the lock(e.g., as detected by the geofence management module 210) within thescheduled time range, the submission of completed forms and documents bya user of the client device 110 or other authorized user, and timingconditions (e.g., a lock 140 may be disabled within a set time window).The lock assignment module 220 tracks the progress of the conditionsassociated with each lock 140 and can determine whether a lock 140 isauthorized to be disabled when a request for disabling the lock 140 isreceived by the device communication module 205 based on the storedinformation about whether the conditions have been met. In someembodiments, the lock assignment module 220 may transmit a communicationto an application of the client device 110 to display information to auser identifying incomplete documents that will need to be completed andsubmitted to disable the lock 140.

The lock assignment datastore 225 stores the data from the lockassignment module 220 about lock 140 assignments and conditionsassociated with locks 140. Scheduling information associating a specificlock 140 with a user of a client device 110 is stored in the lockassignment datastore 225 when the assignment is established. The lockassignment module 220 also accesses information about the scheduled lock140 assignments to determine which locks 140 will be available forassignment at the required time. In addition to the lock 140assignments, the lock assignment datastore 225 may store executeddocuments, submitted forms, information about the current location ofthe client device 110 in relation to the geofence boundary of the lock140, and other data associated with conditions for disabling the lock.The lock assignment datastore 225 may also store documents,questionnaires, and other forms that a user may need to complete to meetconditions for disabling a lock 140. If a request to disable the lock isreceived at the device communication module 205 and the lock assignmentmodule 220 determines that some conditions have not been met, the devicecommunication module 205 may access the required forms at the lockassignment datastore 225 and send the forms to the client device 110 forthe user to complete and submit. In some embodiments, the physical lockinterface system 130 may have a separate datastore for storingdocumentation related to lock 140 access and assignments by users.

The lock identification module 230 helps a user to identify the assignedlock 140. A user approaching a lock 140 may not know where the lock 140is located or which of a plurality of locks 140 will open in response toa request to disable the assigned lock 140. For example, in a vault withmany rows of safety deposit boxes with locks 140, it may be difficultfor a user unfamiliar with the space to quickly identify a box and lock140. As another example in a rental car center, a lockbox and associatedlock 140 assigned to a user for picking up a key for the rental may be adifferent lockbox from the box assigned to the user for dropping off thekey when returning the vehicle. As a third example, a user of abikeshare program may be notified by an application that the user iswithin a geofence boundary of an available locked bicycle, but may notbe sure of the exact location of the bicycle. When the devicecommunication module 205 receives a request from a user of a clientdevice 110 or an operator device 115 to disable a lock 140, the lockidentification module 230 may activate a lock identifier at or near tothe lock 140. Lock identifiers may include blinking lights, coloredlights, alert sounds, screens displaying identifying information,mechanical indications, or other features for specifying the correctlock 140. For example, a lock 140 on a safety deposit box may blink alight, a screen on a lockbox at a rental car center may flash anddisplay the user's name, and a lock 140 on a bike share bicycle may beepto alert the user to the location of the bike. In one embodiment, anapplication of the client device 110 or operator device 115 may supportaugmented reality features that help the user to identify an assignedlock 140. For example, the user may hold the user device 110 up tocapture and display video of a set of locks 140, and the augmentedreality system may overlay an indication of the lock 140 assigned to theuser in the displayed video stream. In some cases, the lockidentification module 230 may not activate a lock identifier until auser of the client device 110 or operator device 115 transmits a signalrequesting for the lock 140 to be identified.

The signal detection module 235 receives and processes signalsrequesting for the lock 140 to be enabled or disabled. In someembodiments, the signal detection module 235 may be a part of the devicecommunication module 205. The signal detection module 235 monitorscommunications received at the device communication module 205 anddetermines when an application on a client device 110 or operator device115 sends a signal requesting to disable a lock 140. In some cases, anapplication associated with the physical lock interface system 130 mayonly allow a user to send a signal to disable the lock 140 afterconditions associated with disabling the lock have been met or when theuser is prepared to open the lock. For example, a user may have met therequirements for disabling a lock 140 be being within the geofenceboundary, but may not currently want to disable the lock, in such cases,the physical lock interface system 130 may wait until a signal todisable the lock 140 is received at the signal detection module 235. Thesignal detection module 235 communicates with the lock management module240 to enable or disable the physical lock 140.

The lock management module 240 enables and disables the locks 140 inresponse to signals received from the signal detection module 235. Thegeofence management module 210, lock assignment module 220, and signaldetection module 235 detect whether a user associated with a clientdevice 110 or operator device 115 is within a designated geofenceboundary associated with the lock 140 assigned to the user, hasfulfilled any additional conditions for disabling the lock 140, and hasrequested for the lock 140 to be disabled, for example, by transmittingan electronic signal. In various embodiments, any alternate combinationsof information from modules and devices associated with the physicallock interface system 130 may be used by the physical lock interfacesystem 130 to determine that a lock 140 can be disabled. In response,the lock management module transmits a signal to the lock 140 mechanismto disable the lock. The lock management module 240 also interacts withlocks 140 to enable lock 140 mechanisms. Similarly to disabling a lock140, the lock management module 240 may have various conditions forenabling a lock 140. Such conditions may be monitored by the geofencemanagement module 210, lock assignment module 220, and signal detectionmodule 235 and may vary depending on the use case of the lock 140.

The lock interaction detection system 245 interfaces with sensors anddetectors that may be associated with a lock 140 to detect and verifylock 140 interactions. In some example embodiments, the lock interactiondetection system 245 comprises sensors that can determine if one or morelocks 140 has been physically enabled, disabled, or tampered with.Sensors may include motion sensors, video recordings, and magnetic orother mechanical sensors. The lock interaction detection system 245communicates with the lock management module 240 when a sensor detectsan interaction with a lock 140. If the lock interaction is not expected(i.e., the lock management module 240 did not send a correspondingsignal to enable or disable the lock 140), the lock interactiondetection system 245 may communicate with an operator device 115 toalert operators to the unauthorized lock 140 activity. In some cases,the lock interaction detection system 245 may also notify operatordevices 115 of some or all detected lock 140 interactions, includingscheduled and authorized lock 140 interactions. In some embodiments, thelock interaction detection system 245 may communicate with other modulesof the physical lock interface system 130 to enable a lock 140 ifunauthorized or unusual activity is detected in relation to the lock140. For example, responsive to detecting that a lock has been tamperedwith, the lock interaction detection system 245 may request that thelock management module 240 enable the lock 140, and may request that thelock assignment module 220 add additional conditions to the lock 140assignment for disabling the lock. Example additional conditions mayinclude receipt of authorization from an operator device 115 that thelock 140 may be disabled and/or extra authentication via an applicationof the client device 110 to confirm that the user of the client device110 is involved in disabling the lock 140. For example, the devicecommunication module 205 may send a two-factor authentication message ora verification code to a verified account associated with the user ofthe client device 110 requesting access to the lock 140.

In some embodiments, the physical lock interface system 130 includes anoriginal equipment manufacturer (OEM) communication module 250. The OEMcommunication module 250 provides a way for the physical lock interfacesystem 130 to communicate requests and instructions to equipmentassociated with the locks 140. For example, a physical lock interfacesystem 130 associated with lockboxes for keys at a car dealership may beable to communicate with the OEM systems of vehicles at the dealershipusing the OEM communication module 250. The OEM communication module 250may provide extra layers of security and authorization for the equipmentthat is secured by the locks 140 of the physical lock interface system130. Expanding on the car dealership example, the dealership may provideloaner vehicles that a user can drive while their car is being serviced.To allow the user to pick up the loaner vehicle at their convenience,the key to the loaner vehicle may be stored in a lockbox secured by alock 140 and assigned by the lock assignment module 220 to the clientdevice 110 associated with the user renting the vehicle. If the lockinteraction detection system 245 detects unauthorized access ortampering with the lock 140, the OEM communication module 250 cancommunicate with the OEM systems to request that an onboard computer onthe rental vehicle disables access, operation, or ignition of thevehicle itself until an operator has authorized the access or until atwo-factor authentication has confirmed that the correct user haspossession of the vehicle keys. Communications by the OEM communicationmodule 250 can vary depending on the type of equipment that isassociated with the locks 140.

The OEM communication module 250 or another module of the physical lockinterface system 130 (e.g., such as the device communication module 205)manages authorization and verification of users of the client devices110 and users of the operator devices 115. The physical lock interfacesystem 130 may require verification of an authorized user to enable ordisable a lock 140 or to disable extra security from an OEM system. Toverify a user, the physical lock interface system 130 communicatesinstructions to an application installed on the client device 110 (oroperator device 115) that is associated with the physical lock interfacesystem 130 to prompt the user of the client device 110 to take an extrastep that will be needed to access the items secured by the lock 140 orotherwise managed by the physical lock interface system. In someembodiments, rather than a prompt or notification from an application,the user may receive information about additional verification steps viaa text message, phone call, email, or other messaging format. In oneembodiment, the physical lock interface system 130 uses multi-factorauthentication to verify a user. For example, the prompt, notification,or message sent to a verified user account, address, or phone numberassociated with the client device 110 may include a code or othermessage. The user inputs the code or other message in a prompt either atthe application of the client device 110 associated with the physicallock interface system 130, or at another input location such as at thelock 140. When the user is verified (e.g., upon receipt of a verifiedcode or message), the physical lock interface system 130 may proceed todisable or enable a lock 140, or may communicate via the OEMcommunication module 250 to provide access to a secured system. Forexample, when a user is verified, OEM communication module 250communicates with OEM system to release whatever extra security measurewas instituted (such as preventing access or ignition to a vehiclewithout verification of the user).

FIG. 3 illustrates a system environment for locks 140 associated withthe physical lock interface system 130, in accordance with an exampleembodiment. In the example of FIG. 3 , a physical lock interface system130 manages a set of eight lockboxes, each secured by a lock 140 (i.e.,locks 140A, 140B, 140C, 140D, 140E, 140F, 140G, and 140H). A user 300 ofa client device 110 has entered a geofence boundary 310, depicted by adashed circle. The user 300, is depicted in FIG. 3 as a stick figurerepresenting a person, but the user 300 could also be a car or othervehicle. The geofence boundary 310 is associated with one or more of thelocks 140 by the geofence management module 210. The geofence managementmodule 210 detects that the user 300 is within the geofence boundary(e.g., using facial recognition to identify the user, or by verifying alicense place image of a car of the user). The user 300 approaches thelockboxes (e.g., a wall of lockboxes as depicted in FIG. 3 or one ormore lockboxes in another configuration) and transmits a request toidentify the lockbox and lock 140 associated with the user 300 via anapplication on the client device 110. In response, the lockidentification module 230 causes a light at lock 140G to blink (asdepicted by a bold outline in FIG. 3 ). The user 300, being within thegeofence boundary 310 and having located the lockbox and lock 140G,sends, via the application on the client device 110, a request signal tothe signal detection module 235 to disable the lock 140G so that theuser 300 can open the lockbox. The lock assignment module 220 determineswhether the user 300 has completed the conditions associated withdisabling the lock 140, and once the conditions are met, the lockmanagement module 240 transmits a signal to the lock 140G to disable thelock.

FIG. 4 is a block diagram illustrating components of an example machineable to read instructions from a machine-readable medium and executethem in one or more processors (or controllers). Specifically, FIG. 4shows a diagrammatic representation of the physical lock interfacesystem 130 in the example form of a computer system 400. The computersystem 400 can be used to execute instructions 424 (e.g., program codeor software) for causing the machine to perform any one or more of themethodologies (or processes) described herein. In alternativeembodiments, the machine operates as a standalone device or a connected(e.g., networked) device that connects to other machines. In a networkeddeployment, the machine may operate in the capacity of a server machineor a client machine in a server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a set-top box (STB), a smartphone, aninternet of things (IoT) appliance, a network router, switch or bridge,or any machine capable of executing instructions 424 (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute instructions 424 to perform any one or more of themethodologies discussed herein.

The example computer system 400 includes one or more processing units(generally processor 402). The processor 402 is, for example, a centralprocessing unit (CPU), a graphics processing unit (GPU), a digitalsignal processor (DSP), a controller, a state machine, one or moreapplication specific integrated circuits (ASICs), one or moreradio-frequency integrated circuits (RFICs), or any combination ofthese. The computer system 400 also includes a main memory 404. Thecomputer system may include a storage unit 416. The processor 402,memory 404, and the storage unit 416 communicate via a bus 408.

In addition, the computer system 406 can include a static memory 406, agraphics display 410 (e.g., to drive a plasma display panel (PDP), aliquid crystal display (LCD), or a projector). The computer system 400may also include alphanumeric input device 412 (e.g., a keyboard), acursor control device 414 (e.g., a mouse, a trackball, a joystick, amotion sensor, or other pointing instrument), a signal generation device418 (e.g., a speaker), and a network interface device 420, which alsoare configured to communicate via the bus 408.

The storage unit 416 includes a machine-readable medium 422 on which isstored instructions 424 (e.g., software) embodying any one or more ofthe methodologies or functions described herein. For example, theinstructions 424 may include instructions for implementing thefunctionalities of the device communication module 205, the geofencemanagement module 210, the lock assignment module 220, the lockidentification module 230, the signal detection module 235, the lockmanagement module 240, the lock detection system 245, and the OEMcommunication module 250. The instructions 424 may also reside,completely or at least partially, within the main memory 404 or withinthe processor 402 (e.g., within a processor's cache memory) duringexecution thereof by the computer system 400, the main memory 404 andthe processor 402 also constituting machine-readable media. Theinstructions 424 may be transmitted or received over a network 426, suchas the network 120, via the network interface device 420.

While machine-readable medium 422 is shown in an example embodiment tobe a single medium, the term “machine-readable medium” should be takento include a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storethe instructions 424. The term “machine-readable medium” shall also betaken to include any medium that is capable of storing instructions 424for execution by the machine and that cause the machine to perform anyone or more of the methodologies disclosed herein. The term“machine-readable medium” includes, but not be limited to, datarepositories in the form of solid-state memories, optical media, andmagnetic media.

FIG. 5 is a flowchart illustrating a method facilitating disablement ofa physical lock, in accordance with an example embodiment. The steps ofthe flowchart may be performed in processors 402 of a computer system400 comprising a physical lock interface system 130. The physical lockinterface system 130 receives 510 a request to enable a user to disablea physical lock 140 during a particular range of time. For example, therequest may be for scheduling a time range in which the user can accessand interact with the lock 140. The lock 140 is associated with aboundary defined by a geofence 310. During the range of time, thegeofence management module 210 or another module of the physical lockinterface system 130 monitors 520 for a presence of the user within thegeofence boundary. In response to determining that the user is withinthe geofence during the range of time, the physical lock interfacesystem 130 transmits 530 a communication to an application of a clientdevice of the user. The application of the client device 110 of the useris configured to interact electronically with the physical lock 140. Insome embodiments, the client device 110 interacts electronically withthe physical lock 140 via modules of the physical lock interface system130 such as the lock management module 240. The application of theclient device 110 may also be configured to display information thatidentifies the physical lock 140 based on the transmitted communication.The physical lock interface system 130 detects 540 an electronic signalinitiated by the application on the client device 110 while the user iswithin the geofence boundary. In response to detecting the electronicsignal, the lock management module 240 disables the physical lock 140.In various embodiments, an operator device 115 may interact with thephysical lock interface system 130 in the same way as the client device110.

The foregoing description of the embodiments has been presented for thepurpose of illustration; it is not intended to be exhaustive or to limitthe patent rights to the precise forms disclosed. Persons skilled in therelevant art can appreciate that many modifications and variations arepossible in light of the above disclosure.

Some portions of this description describe the embodiments in terms ofalgorithms and symbolic representations of operations on information.These algorithmic descriptions and representations are commonly used bythose skilled in the data processing arts to convey the substance oftheir work effectively to others skilled in the art. These operations,while described functionally, computationally, or logically, areunderstood to be implemented by computer programs or equivalentelectrical circuits, microcode, or the like. Furthermore, it has alsoproven convenient at times, to refer to these arrangements of operationsas modules, without loss of generality. The described operations andtheir associated modules may be embodied in software, firmware,hardware, or any combinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by one or more computer processors for performingany or all of the steps, operations, or processes described.

Embodiments may also relate to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, and/or it may comprise a computing device selectivelyactivated or reconfigured by a computer program stored in the computer.Such a computer program may be stored in a non-transitory, tangiblecomputer readable storage medium, or any type of media suitable forstoring electronic instructions, which may be coupled to a computersystem bus. For instance, a computing device coupled to a data storagedevice storing the computer program can correspond to a special-purposecomputing device. Furthermore, any computing systems referred to in thespecification may include a single processor or may be architecturesemploying multiple processor designs for increased computing capability.

Embodiments may also relate to a product that is produced by a computingprocess described herein. Such a product may comprise informationresulting from a computing process, where the information is stored on anon-transitory, tangible computer readable storage medium and mayinclude any embodiment of a computer program product or other datacombination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the patent rights be limitednot by this detailed description, but rather by any claims that issue onan application based hereon. Accordingly, the disclosure of theembodiments is intended to be illustrative, but not limiting, of thescope of the patent rights, which is set forth in the following claims.

What is claimed is:
 1. A method comprising: receiving a request toenable a user to disable a physical lock during a particular range oftime, the request entered by the user into a user interface, the userinterface receiving an indication of the particular range of time, thephysical lock being associated with a boundary defined by a geofence andthe physical lock being one of a plurality of physical locks that are atdifferent locations within the boundary; at a beginning of the range oftime, initiating a monitoring for a presence of the user within thegeofence, the monitoring continuing until an end of the range of time;in response to determining, based on the monitoring, that the user iswithin the geofence during the range of time, transmitting acommunication to an application of a client device of the user, theapplication configured to interact electronically with the physicallock, the application configured to cause the client device to displayinformation identifying a location of the physical lock from among theplurality of physical locks that are at different locations within theboundary based on the communication; detecting an electronic signalinitiated by the application while the user is within the geofence; andresponsive to detecting the electronic signal, disabling the physicallock.
 2. The method of claim 1, wherein the physical lock, whendisabled, provides access to the user to a physical key for accessing avehicle, and wherein the method further comprises: prior to detectingthe electronic signal initiated by the application while the user iswithin the geofence, detecting a disabling of the physical lock; andresponsive to detecting the disabling of the physical lock prior todetecting the electronic signal initiated by the application while theuser is within the geofence, transmitting a communication to a server toprevent access to a vehicle by way of the physical key withoutadditional verification.
 3. The method of claim 2, further comprising:transmitting a communication to the to the application of the clientdevice to cause the client device to display a request for the user toenter a verification code; receiving the additional verificationcomprising the verification code; and responsive to the receipt of theadditional verification, transmitting a communication to the server toenable access to the vehicle by way of the physical key.
 4. The methodof claim 1, wherein monitoring for a presence of the user furthercomprises: receiving a photo of an area within the boundary defined bythe geofence from a camera that is positioned to capture images ofvehicles entering the boundary defined by the geofence; analyzing thephoto to determine a unique identifier of a vehicle shown in the photo;and determining that the unique identifier of the vehicle matches aunique identifier of a vehicle that is known to be associated with theuser.
 5. The method of claim 1, further comprising, prior to disablingthe physical lock: determining one or more documents of a predefined setof documents has not been completed by the user; transmitting acommunication to the application of the client device to cause theclient device to display information identifying the one or moreincomplete documents; and determining that the one or more incompletedocuments are subsequently completed by the user.
 6. The method of claim1, further comprising: in response to determining that the user iswithin the geofence during the range of time, transmitting acommunication to the application of the client device of the user torender for display to the user, instructions for disabling the physicallock.
 7. The method of claim 1, further comprising: in response todetermining that the user is within the geofence during the range oftime, transmitting a communication to a system that manages the physicallock to activate a light associated with the physical lock, the lightidentifying the physical lock from among the plurality of physicallocks.
 8. The method of claim 1, further comprising: prior to detectingthe electronic signal initiated by the application while the user iswithin the geofence, detecting a disabling of the physical lock; andresponsive to detecting the disabling of the physical lock prior todetecting the electronic signal initiated by the application while theuser is within the geofence, transmitting a communication to anapplication of a client device of an operator associated with managementof the physical lock, the application configured to cause the clientdevice of the operator to display information identifying the physicallock based on the detection, the communication including instructions todisplay the information identifying the physical lock based on thedetection.
 9. A non-transitory computer-readable medium comprisingmemory with instructions encoded thereon, the instructions, whenexecuted by one or more processors, causing the one or more processorsto perform operations, the instructions comprising instructions to:receive a request to enable a user to disable a physical lock during aparticular range of time, the request entered by the user into a userinterface, the user interface receiving an indication of the particularrange of time, the physical lock being associated with a boundarydefined by a geofence and the physical lock being one of a plurality ofphysical locks that are at different locations within the boundary; at abeginning of the range of time, initiate a monitoring for a presence ofthe user within the geofence, the monitoring continuing until an end ofthe range of time; in response to determining, based on the monitoring,that the user is within the geofence during the range of time, transmita communication to an application of a client device of the user, theapplication configured to interact electronically with the physicallock, the application configured to cause the client device to displayinformation identifying a location of the physical lock from among theplurality of physical locks that are at different locations within theboundary based on the communication; detect an electronic signalinitiated by the application while the user is within the geofence; andresponsive to detecting the electronic signal, disable the physicallock.
 10. The non-transitory computer-readable medium of claim 9,wherein the physical lock, when disabled, provides access to the user toa physical key for accessing a vehicle, and wherein the instructionsfurther comprise instructions to: prior to detecting the electronicsignal initiated by the application while the user is within thegeofence, detect a disabling of the physical lock; and responsive todetecting the disabling of the physical lock prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, transmit a communication to a server to prevent access toa vehicle by way of the physical key without additional verification.11. The non-transitory computer-readable medium of claim 10, theinstructions further comprising instructions to: transmit acommunication to the to the application of the client device to causethe client device to display a request for the user to enter averification code; receive the additional verification comprising theverification code; and responsive to the receipt of the additionalverification, transmit a communication to the server to enable access tothe vehicle by way of the physical key.
 12. The non-transitorycomputer-readable medium of claim 9, wherein the instructions to monitorfor a presence of the user further comprise instructions to: receive aphoto of an area within the boundary defined by the geofence from acamera that is positioned to capture images of vehicles entering theboundary defined by the geofence; analyze the photo to determine aunique identifier of a vehicle shown in the photo; and determine thatthe unique identifier of the vehicle matches a unique identifier of avehicle that is known to be associated with the user.
 13. Thenon-transitory computer-readable medium of claim 9, the instructionsfurther comprising, prior to disabling the physical lock, instructionsto: determine one or more documents of a predefined set of documents hasnot been completed by the user; transmit a communication to theapplication of the client device to cause the client device to displayinformation identifying the one or more incomplete documents; anddetermine that the one or more incomplete documents are subsequentlycompleted by the user.
 14. The non-transitory computer-readable mediumof claim 9, the instructions further comprising instructions to: inresponse to determining that the user is within the geofence during therange of time, transmit a communication to the application of the clientdevice of the user to render for display to the user, instructions fordisabling the physical lock.
 15. The non-transitory computer-readablemedium of claim 9, the instructions further comprising instructions to:in response to determining that the user is within the geofence duringthe range of time, transmit a communication to a system that manages thephysical lock to activate a light associated with the physical lock, thelight identifying the physical lock from among the plurality of physicallocks.
 16. The non-transitory computer-readable medium of claim 9, theinstructions further comprising instructions to: prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, detect a disabling of the physical lock; and responsive todetecting the disabling of the physical lock prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, transmit a communication to an application of a clientdevice of an operator associated with management of the physical lock,the application configured to cause the client device of the operator todisplay information identifying the physical lock based on thedetection, the communication including instructions to display theinformation identifying the physical lock based on the detection.
 17. Asystem comprising: a non-transitory computer-readable medium comprisingmemory with instructions encoded thereon; and one or more processorsthat, when executing the instructions, are caused to perform operationscomprising: receiving a request to enable a user to disable a physicallock during a particular range of time, the request entered by the userinto a user interface, the user interface receiving an indication of theparticular range of time, the physical lock being associated with aboundary defined by a geofence and the physical lock being one of aplurality of physical locks that are at different locations within theboundary; at a beginning of the range of time, initiating a monitoringfor a presence of the user within the geofence, the monitoringcontinuing until an end of the range of time; in response todetermining, based on the monitoring, that the user is within thegeofence during the range of time, transmitting a communication to anapplication of a client device of the user, the application configuredto interact electronically with the physical lock, the applicationconfigured to cause the client device to display information identifyinga location of the physical lock from among the plurality of physicallocks that are at different locations within the boundary based on thecommunication; detecting an electronic signal initiated by theapplication while the user is within the geofence; and responsive todetecting the electronic signal, disabling the physical lock.
 18. Thesystem of claim 17, wherein the physical lock, when disabled, providesaccess to the user to a physical key for accessing a vehicle, andwherein the processors, when executing the instructions, are furthercaused to perform operations comprising: prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, detecting a disabling of the physical lock; and responsiveto detecting the disabling of the physical lock prior to detecting theelectronic signal initiated by the application while the user is withinthe geofence, transmitting a communication to a server to prevent accessto a vehicle by way of the physical key without additional verification.19. The system of claim 18, the processors, when executing theinstructions, further caused to perform operations comprising:transmitting a communication to the to the application of the clientdevice to cause the client device to display a request for the user toenter a verification code; receiving the additional verificationcomprising the verification code; and responsive to the receipt of theadditional verification, transmitting a communication to the server toenable access to the vehicle by way of the physical key.
 20. The systemof claim 17, wherein instructions for monitoring for a presence of theuser, when executed by the one or more processors, further cause the oneor more processors to perform operations comprising: receiving a photoof an area within the boundary defined by the geofence from a camerathat is positioned to capture images of vehicles entering the boundarydefined by the geofence; analyzing the photo to determine a uniqueidentifier of a vehicle shown in the photo; and determining that theunique identifier of the vehicle matches a unique identifier of avehicle that is known to be associated with the user.